- Severity: Low
- Status: Open
- Details: `getDisabledMatcher()` calls `stackAsyncTask("runtime_disabled_matcher", ...)` with a hardcoded string key. The `stacks` map in `async_queue.ts` is module-global. In production (single SW process, one RuntimeService), this is harmless. In tests that run concurrent `describe` blocks, multiple RuntimeService instances share this queue — their tasks are serialized unnecessarily. Correctness is maintained (each task closes over its own `this`), but cross-instance queue coupling is a latent fragility and harms parallel test throughput.
- Required action: Replace the hard-coded key with a per-instance unique string (e.g. `this.instanceId` set in the constructor via `crypto.randomUUID()` or a counter, used as `runtime_disabled_matcher:${this.instanceId}`).

- Severity: Low
- Status: Open
- Details: `runtime.ts` line 1151 (the JSDoc block above `buildDisabledMatcher`): "require disabledMatcherVersion **intergrity** check." is a misspelling of "integrity".
- Required action: Fix the typo.

- Severity: Note
- Status: Open
- Details: `updateSorter()` always calls `invalidateDisabledMatcher()` internally. In the `deleteScripts` listener (runtime.ts ~line 583), the explicit `this.invalidateDisabledMatcher()` before `this.updateSorter(...)` is redundant because both calls happen synchronously before any `await`. (By contrast, in `installScript` the explicit early call is necessary because `updateSorter` is deferred until after an `await scriptDAO.get()`.) The redundancy is harmless but slightly misleading about why the pattern is used.
- Required action: None strictly required. A short inline comment distinguishing the redundant-but-defensive call from the necessary early-call pattern (as in installScript) would help readers understand intent. Acceptable to leave as-is.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>